Electronic ticketing system

ABSTRACT

The present invention is directed towards an electronic ticket suitable for providing entry to an event. The electronic ticket is capable of being stored, in electronic format, on a mobile user device. The electronic ticket comprises a dynamic entry code for the event such that the dynamic entry code is transitionable from an inoperable state to a functional state, whereby entry to the event is only possible when the dynamic entry code has been transitioned to the functional state. The dynamic entry code is a visual code which is non-readable by humans and is stored in a memory of the mobile user device, such that the inoperable state of the dynamic entry code prohibits the visual code from being displayed by the mobile user device and the functional state of the dynamic entry code permits the visual code to be displayed by the mobile user. The advantage of providing the dynamic entry code is that the electronic ticket can hide the entry code until close to the event start time so that a ticket tout will find it difficult to sell the ticket on as a purchaser would have less confidence in buying a ticket which does not display the entry code required for admission. Moreover, a ticket fraudster cannot duplicate the ticket.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a national phase to PCT Application No.PCT/EP2017/062049 filed May 18, 2017, which in turn claims priority toUK Patent Application No. GB1608749.6 filed May 18, 2016, bothapplications being incorporated in their entirety herein by referencethereto.

FEDERALLY SPONSORED RESEARCH AND DEVELOPMENT

None.

BACKGROUND OF THE INVENTION 1. Field of the Invention

This invention relates to an electronic ticketing system and method forproviding electronic tickets for an event, which facilitates apossibility for trustworthy re-sale of the electronic tickets.

2. Background

Throughout this specification, the term “electronic ticket” andassociated derivations of same shall be understood to encompass any typeof ticket or pass or code which is maintained in electronic format foruse, and will permit admission to an event. It will be understood thatthe event referred to through the specification can be any type oflimited admission event such as a sports match, music gig, and so on.

Tickets for large-scale events are typically sold by primary ticketagents for a defined market price. However, there is a problem wheretickets fall into the hands of individuals and companies who seek tore-sell tickets for popular events at inflated prices. These individualsare sometimes referred to as ticket touts or scalpers. These tickettouts are able to make a profit by purchasing a number of tickets fromthe primary ticket agent, using a team of people or software which canbe used to purchase tickets in an automated fashion using onlineticketing websites. The ticket touts then re-sell the tickets on asecondary market at an inflated price, for an amount exceeding thedefined market price.

This is undesirable as genuine fans, members of the public, and eventgoers in general can oftentimes find themselves unable to purchasetickets for an event as the ticket touts have been able to act in a veryspeedy fashion to secure large quantities of the tickets and will onlyre-sell the tickets to the event goers at inflated prices. Of course,many genuine fans cannot afford the tickets at the inflated prices.

Although there have been attempts to curb this activity, such aslimiting the maximum number of tickets each person can buy, the problemstill exists. The ticket touts easily circumvent limited ticket salerules by creating multiple accounts and/or using multiple credit cardsor multiple payment services.

The tickets are usually a hardcopy ticket which is printed on paper or alight cardboard and contains a static entry code, such as a barcode orQR code. More recently, tickets have started to be issuedelectronically, which are then printed off by the user to create ahardcopy ticket, or alternatively the electronic ticket can be displayedon a screen of a mobile user device. Again, a static entry code isdisplayed on the screen for such electronic tickets that are not printedoff.

The static entry code is read by a scanner and entrance to the event isallowed if the code scans successfully.

As the entry code is static, it is easy for a fraudster to createmultiple copies of seemingly legitimate tickets and sell these seeminglylegitimate tickets to unsuspecting fans. The unsuspecting fans will onlyrealize there is an issue with the ticket when they attempt entry to theevent.

Furthermore, a purchaser will feel more confident when purchasing aticket on the secondary market when the ticket has a static code as theymay be able to compare the ticket from a ticket tout to a ticket theyknow to be genuine. This confidence is important as without it, a tickettout would find it more difficult to sell tickets on the secondarymarket.

Thus, ticket fraud and re-selling of tickets is more difficult toprevent when static entry codes are used. A solution is sought to theproblem of ticket touting and ticket fraud. Moreover, a solution whichdoes not eliminate the possibility of re-selling a ticket is sought asre-selling a ticket is occasionally necessary and is for a legitimatereason.

One of the problems with ticket re-selling is that it is difficult todifferentiate a genuine fan from a ticket tout from a ticket fraudster.There is effectively no difference, in transactional terms, between agenuine fan re-selling their ticket at the defined market price and aticket tout re-selling a ticket at an inflated price. This problem isfurther compounded by the use of the static entry codes which facilitatethe relatively easy re-selling of tickets by ticket touts and ticketduplication and ticket forging by fraudsters.

It is a goal of the present invention to provide a method of providingelectronic tickets and a ticketing system that overcomes at least one ofthe above mentioned problems.

SUMMARY OF THE INVENTION

The present invention is directed towards an electronic ticket suitablefor providing entry to an event, the electronic ticket capable of beingstored on a mobile user device, wherein the electronic ticket comprisesa dynamic entry code for the event such that the dynamic entry code istransitionable from an inoperable state to a functional state, wherebyentry to the event is only possible when the dynamic entry code has beentransitioned to the functional state; wherein, the dynamic entry code isa visual code which is non-readable by humans, such that the inoperablestate of the dynamic entry code prohibits the visual code from beingdisplayed by the mobile user device and the functional state of thedynamic entry code permits the visual code to be displayed by the mobileuser.

The advantage of providing the dynamic entry code is that the electronicticket can hide the entry code until close to the event start time sothat a ticket tout will find it difficult to sell the ticket on as apurchaser would have less confidence in buying a ticket which does notdisplay the entry code required for admission. Moreover, a ticketfraudster cannot duplicate the ticket.

In a further embodiment, at the time of purchase the electronic ticketis assigned to one or more of: a ticket holder's name, a ticket holder'stelephone number, and/or a ticket holder's device ID, such that, priorto allowing the dynamic entry code to be transitioned from theinoperable state to the functional state, one or more of the ticketholder's name, the ticket holder's telephone number, and/or the ticketholder's device ID is checked to ensure a match with a name associatedwith the mobile user device, a telephone number of the mobile userdevice, and/or a device ID of the mobile user device, respectively.

In a further embodiment, the electronic ticket is assigned to a ticketholder's name at a time of purchase.

In a further embodiment, the electronic ticket is assigned to a ticketholder's telephone number at a time of purchase.

In a further embodiment, the electronic ticket is assigned to a ticketholder's name and a ticket holder's telephone number at a time ofpurchase.

In a further embodiment, the electronic ticket is assigned to a ticketholder's device ID at a time of purchase.

In a further embodiment, the electronic ticket is assigned to a ticketholder's name and a ticket holder's telephone number and a ticketholder's device ID at a time of purchase.

In a further embodiment, the ticket holder's telephone number assignedto the electronic ticket must match the telephone number of the mobileuser device in order to allow the dynamic entry code to transition fromthe inoperable state to the functional state.

In a further embodiment, the ticket holder's telephone number assignedto the electronic ticket must match the telephone number of the mobileuser device in order to allow the dynamic entry code to become stored onthe mobile user device.

In a further embodiment, the ticket holder's name and the ticketholder's telephone number assigned to the electronic ticket must matchthe name associated with the user device and the telephone number of themobile user device in order to allow the dynamic entry code totransition from the inoperable state to the functional state.

In a further embodiment, the ticket holder's name and the ticketholder's telephone number assigned to the electronic ticket must matchthe name associated with the user device and the telephone number of themobile user device in order to allow the dynamic entry code to becomestored on the mobile user device.

In a further embodiment, the ticket holder's name and the ticketholder's telephone number and the ticket holder's device ID assigned tothe electronic ticket must match the name associated with the userdevice and the telephone number of the mobile user device and the deviceID of the mobile user device in order to allow the dynamic entry code totransition from the inoperable state to the functional state.

Having such a triple check for identification will reduce the instancesof fraud considerably as it is very difficult for a ticket tout tooperate within an environment where the device ID of a mobile phone mustmatch a device ID of a user account which would have been established atthe time of purchase, and also to match with the telephone number of themobile phone device, and also to match with the name of the ticketholder, where that name could be counter-checked by event staffrequiring photographic identification in that name. The possibility ofthe ticket being sold on by a tout is much less as a result of thistriple check security measure. Even in the above embodiments, where justa name or a telephone number or a device ID, or a combination of any twoof these, is also viewed as a greatly increased security measure.

In a further embodiment, the ticket holder's name and the ticketholder's telephone number and the ticket holder's device ID assigned tothe electronic ticket must match the name associated with the userdevice and the telephone number of the mobile user device and the deviceID of the mobile user device in order to allow the dynamic entry code tobecome stored on the mobile user device.

In a further embodiment, the dynamic entry code is transitioned from theinoperable state to the functional state based on an activator which isphysically located adjacent an entry point of the event.

In a further embodiment, the dynamic entry code is transitioned from theinoperable state to the functional state in response to the mobile userdevice scanning a code which is physically located adjacent an entrypoint of the event.

In a further embodiment, the dynamic entry code is transitioned from theinoperable state to the functional state if a user credibility ratingassociated with the mobile user device is above a predefined threshold.

In a further embodiment, the user credibility rating is calculated basedon a user's historical ticketing transactions.

In a further embodiment, the user's historical ticketing transactionscomprise one or more of: number of tickets purchased; aggregate value oftickets purchased; number of tickets re-sold; aggregate value of ticketsre-sold; number of tickets used; aggregate value of tickets used; numberof tickets not used; aggregate value of tickets not used.

In a further embodiment, the user credibility rating is calculated basedon a ratio of the number of tickets re-sold as compared to the number oftickets used.

In a further embodiment, the user credibility rating is calculated basedon a ratio of the aggregate value of tickets re-sold as compared to theaggregate value of tickets used.

In a further embodiment, the user credibility rating is calculated basedon a ratio of the number of tickets purchased as compared to the numberof tickets re-sold.

In a further embodiment, the electronic ticket is capable of beingmarked as having been used.

In a further embodiment, the electronic ticket is marked as used when aPIN is input to the mobile user device. In a further embodiment, theelectronic ticket is marked as used when an alphanumeric code is inputto the mobile user device. In a further embodiment, the electronicticket is marked as used when a code is scanned into the mobile userdevice.

In a further embodiment, the visual code is a Quick Response (QR) codewhich is only displayed on a screen of the mobile user device when theQR code has been transitioned to the functional state. In a furtherembodiment, the visual code is a barcode which is only displayed on ascreen of the mobile user device when the barcode has been transitionedto the functional state.

The present invention is further directed towards a method of providingan electronic ticket suitable for providing entry to an event, theelectronic ticket capable of being stored on a mobile user device,wherein the method comprises: issuing the electronic ticket, theelectronic ticket comprising a dynamic entry code to allow access to theevent such that the dynamic entry code is transitionable from aninoperable state to a functional state; storing at least a portion ofthe dynamic entry code on the mobile user device, the dynamic entry codecomprising a visual code which is non-readable by humans; transitioningthe dynamic entry code to the functional state to allow entry to theevent; whereby, the inoperable state of the dynamic entry code prohibitsthe visual code from being displayed by the mobile user device and thefunctional state of the dynamic entry code permits the visual code to bedisplayed by the mobile user.

The present invention is further directed towards a method of providingan electronic ticket suitable for providing entry to an event, theelectronic ticket capable of being stored on a mobile user device,wherein the method comprises: assigning, at the time of purchase, theelectronic ticket to one or more of: a ticket holder's name, a ticketholder's telephone number, and/or a ticket holder's device ID; issuingthe electronic ticket, the electronic ticket comprising a dynamic entrycode to allow access to the event such that the dynamic entry code istransitionable from an inoperable state to a functional state; storingat least a portion of the dynamic entry code on the mobile user device,the dynamic entry code comprising a visual code which is non-readable byhumans; checking one or more of the ticket holder's name, the ticketholder's telephone number, and/or the ticket holder's device ID toensure a match with a name associated with the mobile user device, atelephone number of the mobile user device, and/or a device ID of themobile user device, and only allowing the dynamic entry code to betransitioned from the inoperable state to the functional state wheresuch a match exists; transitioning the dynamic entry code to thefunctional state to allow entry to the event; whereby, the inoperablestate of the dynamic entry code prohibits the visual code from beingdisplayed by the mobile user device and the functional state of thedynamic entry code permits the visual code to be displayed by the mobileuser.

In a further embodiment, the method further comprises the step ofassigning the electronic ticket to a ticket holder's name at a time ofpurchase.

In a further embodiment, the method further comprises the step ofassigning the electronic ticket to a ticket holder's name and a ticketholder's telephone number at a time of purchase.

In a further embodiment, the method further comprises the step ofchecking that a ticket holder's telephone number which has been assignedto the electronic ticket matches the telephone number of the mobile userdevice prior to allowing the dynamic entry code to transition from theinoperable state to the functional state.

In a further embodiment, the method further comprises the step ofchecking that a ticket holder's telephone number which has been assignedto the electronic ticket matches the telephone number of the mobile userdevice prior to allowing the dynamic entry code to be stored on themobile user device.

In a further embodiment, the method further comprises the step oftransitioning the dynamic entry code from the inoperable state to thefunctional state subsequent to an interaction with an activator which isphysically located adjacent an entry point of the event.

In a further embodiment, the method further comprises the step oftransitioning the dynamic entry code from the inoperable state to thefunctional state subsequent to the mobile user device scanning a codewhich is physically located adjacent an entry point of the event.

In a further embodiment, the step of transitioning the dynamic entrycode from the inoperable state to the functional state is carried out ifa user credibility rating associated with the mobile user device isabove a predefined threshold.

In a further embodiment, the user credibility rating is calculated basedon a user's historical ticketing transactions.

In a further embodiment, the user's historical ticketing transactionscomprise one or more of: number of tickets purchased; aggregate value oftickets purchased; number of tickets re-sold; aggregate value of ticketsre-sold; number of tickets used; aggregate value of tickets used; numberof tickets not used; aggregate value of tickets not used.

In a further embodiment, the user credibility rating is calculated basedon a ratio of the number of tickets re-sold as compared to the number oftickets used.

In a further embodiment, the user credibility rating is calculated basedon a ratio of the aggregate value of tickets re-sold as compared to theaggregate value of tickets used.

In a further embodiment, the user credibility rating is calculated basedon a ratio of the number of tickets purchased as compared to the numberof tickets re-sold.

In a further embodiment, the method further comprises a step marking theelectronic ticket as having been used, once the electronic ticket hasbeen used to provide entry to the event.

In a further embodiment, the step marking the electronic ticket ashaving been used is carried out by inputting a PIN into the mobile userdevice.

In a further embodiment, the step marking the electronic ticket ashaving been used is carried out by inputting an alphanumeric code intothe mobile user device.

In a further embodiment, the step marking the electronic ticket ashaving been used is carried out by scanning a code into the mobile userdevice.

In a further embodiment, the visual code is a Quick Response (QR) codewhich is only displayed on a screen of the mobile user device when theQR code has been transitioned to the functional state.

In a further embodiment, the visual code is a barcode which is onlydisplayed on a screen of the mobile user device when the barcode hasbeen transitioned to the functional state.

The present invention is further directed to an electronic ticketsuitable for providing entry to an event, the electronic ticket capableof being stored on a mobile user device, wherein the electronic ticketcomprises a dynamic entry code for the event such that the dynamic entrycode is transitionable from an inoperable state to a functional state,whereby entry to the event is only possible when the dynamic entry codehas been transitioned to the functional state.

In a further embodiment, the dynamic entry code is a challenge responsecode stored in a memory of the mobile user device, wherein theinoperable state of the dynamic entry code prohibits the challengeresponse code from being transmitted by the mobile user device and thefunctional state of the dynamic entry code permits the challengeresponse code to be transmitted by the mobile user.

This is particularly advantageous as the ticket fraudster will not beable to forge the tickets as the entry code, even in its functionalstate, will be completely hidden from the fraudster.

In a further embodiment, the dynamic entry code is a visual code storedin a memory of the mobile user device, wherein the inoperable state ofthe dynamic entry code prohibits the visual code from being displayed bythe mobile user device and the functional state of the dynamic entrycode permits the visual code to be displayed by the mobile user. Thisallows the use of legacy scanner machines present at many larger eventvenues.

In a further embodiment, the dynamic entry code stored on the mobileuser device may be altered prior to the dynamic entry code beingtransitioned from the inoperable state to the functional state.

In a further embodiment, the dynamic entry code is transitioned from theinoperable state to the functional state based on a geographicallocation of the mobile user device.

In a further embodiment, the dynamic entry code is transitioned from theinoperable state to the functional state based on the time. The time canpreferably be a server-based time, or a mobile user device-based time.In a further embodiment, the dynamic entry code is transitioned from theinoperable state to the functional state based on the time and on ageographical location of the mobile user device. In a furtherembodiment, the dynamic entry code is transitioned from the inoperablestate to the functional state based on a broadcast command received bythe mobile user device. In a further embodiment, the dynamic entry codeis transitioned from the inoperable state to the functional state basedon a geographical location characteristic. In a further embodiment, thedynamic entry code is transitioned from the inoperable state to thefunctional state based on an activator which is physically locatedadjacent an entry point of the event. In a further embodiment, thedynamic entry code is transitioned from the inoperable state to thefunctional state based on a PIN code which is only known to event staffand may be input into the mobile user device in order to permit theelectronic ticket to be transitioned from the inoperable state to thefunctional state. This feature is useful where connectivity at the venueis insufficient to allow a signal to be received by the mobile userdevice to cause the dynamic entry code to be transitioned from theinoperable state to the functional state.

In a further embodiment, the dynamic entry code is transitioned from theinoperable state to the functional state if a user credibility ratingassociated with the mobile user device is above a predefined threshold.

In a further embodiment, the user credibility rating is calculated basedon a user's historical ticketing transactions.

In a further embodiment, the user's historical ticketing transactionscomprise one of more of: number of tickets purchased; aggregate value oftickets purchased; number of tickets re-sold; aggregate value of ticketsre-sold; number of tickets used; aggregate value of tickets used; numberof tickets not used; aggregate value of tickets not used. In a furtherembodiment, the user credibility rating is calculated based on a ratioof the number of tickets re-sold as compared to the number of ticketsused. In a further embodiment, the user credibility rating is calculatedbased on a ratio of the aggregate value of tickets re-sold as comparedto the aggregate value of tickets used. In a further embodiment, theuser credibility rating is calculated based on a ratio of the number oftickets purchased as compared to the number of tickets re-sold.

In a further embodiment, the visual code is a Quick Response (QR) codewhich is only displayed on a screen of the mobile user device when theQR code has been transitioned to the functional state.

In a further embodiment, the visual code is a barcode which is onlydisplayed on a screen of the mobile user device when the barcode hasbeen transitioned to the functional state.

The present invention is further directed towards a method of providingan electronic ticket suitable for providing entry to an event, theelectronic ticket capable of being stored on a mobile user device,wherein the method comprises; issuing the electronic ticket for storageon the mobile user device, the electronic ticket comprising a dynamicentry code to allow access to the event such that the dynamic entry codeis transitionable from an inoperable state to a functional state; and,transitioning the dynamic entry code to the functional state to allowentry to the event.

In a further embodiment, the dynamic entry code is a challenge responsecode stored in a memory of the mobile user device, wherein theinoperable state of the dynamic entry code prohibits the challengeresponse code from being transmitted by the mobile user device and thefunctional state of the dynamic entry code permits the challengeresponse code to be transmitted by the mobile user.

In a further embodiment, the dynamic entry code is a visual code storedin a memory of the mobile user device, wherein the inoperable state ofthe dynamic entry code prohibits the visual code from being displayed bythe mobile user device and the functional state of the dynamic entrycode permits the visual code to be displayed by the mobile user.

In a further embodiment, the method comprises the step of altering thedynamic entry code stored on the mobile user device prior to the dynamicentry code being transitioned from the inoperable state to thefunctional state.

In a further embodiment, the step of transitioning the dynamic entrycode from the inoperable state to the functional state is carried outbased on a geographical location of the mobile user device. In a furtherembodiment, the step of transitioning the dynamic entry code from theinoperable state to the functional state is carried out based on thetime. In a further embodiment, the step of transitioning the dynamicentry code from the inoperable state to the functional state is carriedout based on the time and on a geographical location of the mobile userdevice. In a further embodiment, the step of transitioning the dynamicentry code from the inoperable state to the functional state is carriedout based on a broadcast command received by the mobile user device. Ina further embodiment, the step of transitioning the dynamic entry codefrom the inoperable state to the functional state is carried out basedon a geographical location characteristic. In a further embodiment, thestep of transitioning the dynamic entry code from the inoperable stateto the functional state is carried out based on an activator which isphysically located adjacent an entry point of the event. In a furtherembodiment, the step of transitioning the dynamic entry code from theinoperable state to the functional state is carried out based on acontrolled trigger. In a preferred embodiment, the controlled trigger isa broadcast command signal receivable by the mobile user device.

In a further embodiment, the step of transitioning the dynamic entrycode from the inoperable state to the functional state is carried out ifa user credibility rating associated with the mobile user device isabove a predefined threshold.

In a further embodiment, the user credibility rating is calculated basedon a user's historical ticketing transactions.

In a further embodiment, the user's historical ticketing transactionscomprise one or more of: number of tickets purchased; aggregate value oftickets purchased; number of tickets re-sold; aggregate value of ticketsre-sold; number of tickets used; aggregate value of tickets used; numberof tickets not used; aggregate value of tickets not used.

In a further embodiment, the user credibility rating is calculated basedon a ratio of the number of tickets re-sold as compared to the number oftickets used. In a further embodiment, the user credibility rating iscalculated based on a ratio of the aggregate value of tickets re-sold ascompared to the aggregate value of tickets used. In a furtherembodiment, the user credibility rating is calculated based on a ratioof the number of tickets purchased as compared to the number of ticketsre-sold.

In a further embodiment, the visual code is a Quick Response (QR) codewhich is only displayed on a screen of the mobile user device when theQR code has been transitioned to the functional state.

In a further embodiment, the visual code is a barcode which is onlydisplayed on a screen of the mobile user device when the barcode hasbeen transitioned to the functional state.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be more clearly understood from the followingdescription of some embodiments thereof, given by way of example only,with reference to the accompanying drawings.

FIG. 1 is a diagrammatic view of a ticketing system in accordance withthe present invention.

FIG. 2 is a flow diagram of the steps involved in purchasing anelectronic ticket in accordance with the ticketing system of the presentinvention.

FIG. 3a is a flow diagram of the steps involved in re-selling anelectronic ticket in a blind re-sale, in accordance with the ticketingsystem of the present invention.

FIG. 3b is a flow diagram of the steps involved in re-selling anelectronic ticket in a direct re-sale, in accordance with the ticketingsystem of the present invention.

FIG. 4a is a front view of a screenshot of an electronic ticket beingdisplayed on a mobile user device, with an entry code of the electronicticket being in an inoperable state.

FIG. 4b is a front view of a screenshot of the electronic ticket of FIG.4a , with the entry code being in a functional state.

FIG. 4c is a front view of a screenshot of the electronic ticket of FIG.4a , with the entry code being in a consumed state.

FIG. 5a is a flow diagram of the steps involved in verifying anelectronic ticket to admit entry to an event, using an entry scannerwhich is communicably connected to a ticketing server of the ticketingsystem of the present invention.

FIG. 5b is a flow diagram of the steps involved in verifying anelectronic ticket to admit entry to an event, using a legacy entryscanner which is not communicably connected to a ticketing server of theticketing system of the present invention.

It is important to appreciate that the present invention is primarilydirected towards a dynamic entry code which forms part of an electronicticket that is capable of being stored on a mobile user device. Thepurpose of the dynamic entry code is to allow the electronic ticket tobe viewed, without displaying or making available the entry code in itsfunctional state. To facilitate this, initially the entry code may bedisplayed and/or stored in an inoperable state which would not permitadmission to an event. Once the dynamic entry code is transitioned fromthe inoperable state to the functional state, the entry code can be usedto gain admission to an event. Aside from this primary aspect of theinvention, the invention is also linked in further embodiments to aticketing system which improves further upon the security of tickets andtheir being linked to verified purchasers, the trustworthiness ofre-selling tickets and purchasing re-sold tickets. Aside from hiding theentry code until a certain location has been reached, or a certain timebefore the event begins in order to mitigate against the ability tore-sell tickets in advance or against the fraudulent forging of tickets,the use of a ticketing system which requires the name of a ticket holderto be provided prior to purchase of the ticket is envisaged. Theticketing system will require the setting up of an account on theticketing system. The user account will be preferably linked to anassociated mobile user device, such as a smartphone or smartwatch or thelike. A device ID, such as an IMEI (International Mobile EquipmentIdentity) or UDID (Unique Device Identifier), may be used as anattribute of a user ID for their account. The user will only be able topurchase tickets using their account on the ticketing system. Suspiciousbehavior can be detected and appropriate action taken against user(s) ofthe ticketing system who re-sell (or gift away) too many of theirtickets or do not purchase and consume their tickets in line with agenerally standard behavior of genuine fans. A user credibility ratingis assigned to each user in this regard.

Referring to FIG. 1, there is provided a ticketing system indicatedgenerally by reference numeral 100. The ticketing system 100 is suitablefor issuing electronic tickets which are to be stored on mobile userdevices and displayed on the mobile user devices in purely electronicform. The tickets issued by the ticketing system 100 of the presentinvention are not envisaged to be printed into a hardcopy form.

The ticketing system 100 comprises a ticketing server 102. The ticketingserver 102 is capable of communicating with an end user app 104 whichwill be installed on a mobile user device (not shown). The ticketingserver 102 will issue an electronic ticket (not shown), comprising adynamic entry code (not shown), which can be viewed on the end user app104. It will be understood that multiple electronic tickets, eachassociated with different events, can be stored on the mobile userdevice. In a preferred embodiment, the electronic tickets are stored ina memory of the mobile user device so that the user does not require adata link to the ticketing server 102 if they wish to view and/or usetheir electronic ticket(s). This could be particularly important ifthere is no network connectivity available in the event location, or, ifthe event is abroad, where data roaming charges may apply.

A venue 106 where a limited admission event, also known as a ticketedevent, will be held is shown in FIG. 1. The event is initially set upvia an event set up portal 108 using a ticketing system portal 110 or aprimary ticket agent's own set up portal 112. Whether the event thesetup using the ticketing system portal 110 or using the primary ticketagent's own server portal 112, the ticketing server 102 will receiveevent information via a communications link 114 regarding the eventincluding the number of tickets which will be made available, thedefined market price of the tickets, and so on.

A user purchases an electronic ticket from a primary ticket agent, whichis a third party portal 118, and which forms part of a larger ticketsales network 116. As the user is being brought through the ticketpurchase process, the third party portal 118 will contact the ticketingserver 102 via a communication link 120. The third party portal 118reserves a ticket with the ticketing server 102 at this point of theprocess.

The user will continue with the ticket purchase process via the thirdparty portal 118 and once a payment process has been successfullycompleted, which will be done via a third party payment gateway (notshown), the electronic ticket will be transferred to the end user app104 via a communications link 126 from the ticketing server 102, The enduser app 104 can be a ticketing system white label app 122 which can beintegrated into an existing venue-related app or ticketing-related app,or, the end user app 104 could be a fully customized ticketing systemapp 124.

In a preferred embodiment, in order to improve the security of thetickets and prevent ticket touting and fraudulent behavior, it will becompulsory for the user to provide a name for each ticket beingpurchased. In this manner, at the time of purchase, a name is associatedwith each ticket being bought. At the point of entry to an event, only aperson having a valid photographic identification, which matches thename associated with the ticket will be admitted entry to the eventusing that ticket. It will be understood that not every person may havetheir identity checked, but the threat to do so will be enough to makeindividuals very hesitant to purchase a ticket for a ticket tout. If aticket is re-sold through the permitted channels, a name change will beallowed on the ticket.

In a further embodiment, it may be compulsory for the user to provide aname and telephone number for each ticket being purchased, or atelephone number for at least one ticket in a batch of tickets beingpurchased simultaneously by a user. In this manner, at the time ofpurchase, a name is associated with each ticket being bought and atelephone number is associated with the ticket (or batch of tickets)being purchased. The system may then only allow a ticket to bedownloaded and stored on a mobile user device, where the telephonenumber of the mobile user device matches the telephone number providedat the time of purchase.

When the electronic ticket has been downloaded and stored onto theuser's mobile user device, the electronic ticket will comprise a dynamicentry code which will initially be stored on the mobile user device inan inoperable state. At an appropriate time and/or geographical locationand/or with a controlled trigger such as a broadcast command from theticketing server or receipt of a trigger code by use of an activatorwhich is physically located adjacent an entry point of the event, thedynamic entry code will be transitioned from the inoperable state into afunctional state. In an alternative embodiment, it is foreseen towithhold a portion of the entry code from storage on the mobile userdevice until the controlled trigger is activated. At such time, thecontrolled trigger will cause the remaining portion of the entry code tobe received by the user's mobile user device and allow the dynamic entrycode to transition from the inoperable state to the functional state. Itwill be appreciated that such an embodiment would only be suitable whereconnectivity with the mobile user device could be substantiallyguaranteed.

Once the electronic ticket has been changed such that its dynamic entrycode has been transitioned from the inoperable state to be functionalstate, the electronic ticket can be presented at a venue 106 forverification. At this point, event staff (not shown) will use aticketing system venue app 128 and inform the ticketing server 102 viacommunication link 132 that the electronic ticket has beenused/consumed. In a preferred embodiment, the ticketing server 102 willinform a venue ticket ledger 130 via a communications link 134 that theelectronic ticket has been found. In this way, the venue 106 will keep arecord of electronic tickets which have been used for an event.

When a user attempts to gain entry to the event 106 by presenting theelectronic ticket, the event staff using the ticketing system venue app128 may be prompted to check the identification of the user. This willbe done randomly, or in line with any event or ticketing system policy,as a user of the ticketing system 100 attempts to gain entry to an eventwhen using an electronic ticket purchased through the ticketing system100. If a ticket does not have a telephone number associated with it,then the event staff may be prompted to check the identification of theuser of that ticket. This could be the case where a batch of ticketswere bought by a lead user, but other members of the group did notassociate their telephone number with their ticket after the purchase,which would be possible to do in a preferred embodiment. The ticketingsystem policy may be alternatively to check a certain percentage ofticket holders. The percentage of identification checks may be increasedor decreased, on-the-fly, in real-time, in response to queue lengths,health and safety instructions for law enforcement, and the like.Moreover, if the ticketing system 100 has detected suspicious behavioron the part of a user, then the user's account may be flagged as a“need-to-check” account and the ticketing server 102 will inform theevent staff via the ticketing system venue app 128 that theidentification of the user needs to be checked as the user is attemptingto gain entry to the event 106. It is also envisaged to perform randomchecks of user's IDs and in general the checking of user's IDs will becarried out in line with an event organizer's policy and/or in line witha policy of the ticketing system 100.

Looking at the ticketing system 100 in more detail, the process ofpurchasing a ticket is shown in FIG. 2. In a first step 206, a user 200selects a ticket for an event which they wish to attend. The ticket forthe event is sold via a third party portal 202. The third party portal202 requests the ticketing server 102 to reserve a ticket in step 208.In step 210, the ticketing server 102 of the present invention willrequest data for the ticket owner. If the user 200 already has aticketing account, the user 200 may log into their account on theticketing server 102 which will automatically populate the requiredticket owner information. Alternatively, the user 200 will be directedto set up a new ticketing account and enter their details. Their detailswill include their name and a mobile telephone number. A mobile userdevice can then be verified via a SMS verification code. The mobile userdevice will then be associated to the user 200. The end user app 104will be installed on the mobile user device. In an alternativeembodiment, the provision of a name and telephone number at the time ofpurchase may be sufficient to allow a user to purchase one or moretickets (with each ticket being associated with a different name at thepoint of purchase) and the user 200 will can then be directed to set upa new ticketing account and enter their details at a later date.

In step 212, the user 200 has provided the details of the ticket ownerto the ticketing server 102. The ticketing server 102 then informs thethird party portal 202 that it is satisfied to issue an electronicticket to the user 200, in step 214. This step may in a preferableembodiment include the step of the ticketing server 102 checking auser's credibility rating (discussed further hereinbelow) prior toinforming the third party portal 202, and only informing the third partyportal 202 that it is satisfied to issue an electronic ticket to theuser 200 if the ticketing server 102 determines that the usercredibility rating is above a predefined threshold. In step 216, thethird party portal 202 request payment from the user 200 via a thirdparty payment gateway 204. In step 218, the third party payment gateway204 requests the user to approve the purchase amount. Once the user 200has approved the purchase amount in step 220, the third party paymentgateway 204 informs the third party portal 202 in step 222 that thepayment has been successfully made. The third party portal 202 theninstructs the ticketing server 102 to issue a ticket, in step 224. Instep 226, the electronic ticket is issued to the end user app 104installed on the mobile user device associated with the ticketingaccount which the user 200 log into or created earlier in the process.Finally, the user 200 is notified of the issuance of the ticket by theend user and 104, in step 228.

In this way, the ticketing server 102 is aware of the ticket owner'sdata for each ticket which allows for monitoring and management of theelectronic tickets. For example, if a user 200 wishes to re-sell theirticket, then the ticketing system 100 is established in such a fashionas to require the engagement of the ticketing server 102 in order tore-sell the ticket in a compliant manner. The electronic tickets may bere-sold within the control and management of the ticketing system 100,as a blind re-sale where the purchaser is not known to the seller, or,as a direct re-sale where the purchaser is known to the seller.

FIG. 3a shows the process which is followed for a blind re-sale, and,FIG. 3b shows the process which is followed for a direct re-sale.

Referring to FIG. 3a , a seller at 300 selects the option to re-selltheir ticket using the end user app 104, in step 302. The end user app104 forwards the ticket re-sell request to ticketing server 102 in step304. In step 306, the third party portal 202 is informed that a ticketfor the event is to be re-sold. It will be understood that the thirdparty portal 202 and the ticketing server 102 may be configured to allowthe re-sale of a ticket at the same price as defined market price, or ata different price to the defined market price. A price range may bepresented to the seller 300, whereas that price range is dictated by thethird party portal 202. Once the third party portal 202 has re-sold theticket, the third party portal 202 in step 308 informs the ticketingserver 102 that the ticket has been re-sold. The ticketing server 102will be aware of the account ID of the purchaser and will issue there-sold ticket to the end user app of the purchaser. At the same time asshown in step 310, the ticketing server 102 will remove the re-soldticket from the end user app 104 of the seller 300. In step 312, theseller 300 is notified by the end user app 104 that the ticket has beensold. Payment for the re-sold ticket will be dealt with separately viathe third party payment gateway (not shown) which will be directed bythe third party portal 202 to make a payment to the seller 300. In analternative embodiment, the re-sale of the ticket by the seller 300could be handled without any need for the third party portal 202 as there-sale process could be handled and accommodated by the ticketingserver 102 itself.

Looking now at FIG. 3b , the seller 300 in step 316 informs the end userapp 104 that they wish to re-sell their ticket to a purchaser 314. Theseller 300 provides the information of the purchaser 314, such as theirticketing account username and/or their mobile telephone number and/ortheir e-mail address and/or their ticketing account identificationnumber. In step 318 this ticket re-sale request afforded to theticketing server 102 which in turn, in step 320, forwards the request tothe third party portal 202. The third party portal 202 forwards aninvitation to the purchaser 314, in step 322, to purchase the tickets ata price defined by the seller 300 which is within the allowable rangeset by the third party portal 202 and/or the ticketing server 102. Instep 324, the purchaser 314 accepts the invitation and purchases theticket. Once the payment from the purchaser 314 has been successfullycompleted, the third party portal 202 informs the ticketing server 102that the re-sale of the tickets have been completed, in step 326. Theticketing server 102 then creates a new ticket in step 328 and issuesthe ticket to the end user app 104 of the purchaser 314. The purchaser314 is notified of the issuance of the ticket in step 330. In step 332,the ticketing server 102 removes the re-sold ticket from the end userapp 104 of the seller 300. The seller 300 is notified in step 334 thatthe ticket has been re-sold and that the re-source ticket has beenremoved from their end user app 104.

In this way, the re-sale of electronic tickets which have been issued inaccordance with the ticketing system 100 of the present invention can bemonitored and managed by the ticketing server 102 of the ticketingsystem 100 of the present invention. The ticketing system 100 will notallow the re-sale of tickets where a user has been determined to beacting in a suspicious manner. The determination of suspicious activitycan be based on a user seeking to re-sell a large number of ticketswhich they have purchased. This is discussed further hereinbelow, whendetailing, the user credibility rating which is calculated for eachuser. The ticketing server 102 can change the ticketing account of sucha user to a “need-to-check” status so that event staff at a venue willcheck the identity of any persons attempting to gain entry to the eventusing a ticket associated with this flagged user account.

In a preferred embodiment, it is envisaged to request a facial image ofa user to be uploaded when creating a user account so that aphotographic identification card can be checked at a venue against thefacial image of the user for that particular user account. However, auser's name may be sufficient in some instances.

Preferably in conjunction with the ticketing system 100 as describedabove, a dynamic entry code is envisaged to be used as part of theelectronic tickets issued by the ticketing system 100. It will beunderstood that the dynamic entry code envisaged as part of thisinvention may operate separately from the ticketing system describedhereinbefore and further hereinbelow. At present, some tickets arepresented electronically and are known to have a dynamic aspect to suchtickets including animations and audio. It is not known from the priorart for an electronic ticket to comprise a dynamic entry code. It isforeseen that the dynamic entry code, which forms the main thrust of thepresent invention, may be used with the electronic tickets known fromthe prior art, without requiring the other elements of the ticketingsystem of the present invention herein described.

Referring now to FIGS. 4a, 4b and 4c , a screenshot of an electronicticket indicated generally by reference numeral 400, which is held on amobile user device, is shown. The electronic ticket 400 comprises eventand/or user information indicated generally by reference numeral 402.The event and/or user information 402 may contain a user's name, theevent's name, the event's location, the event's start time, the venue'sopening time, and so on. Other event information such as an event image406 may be shown or a venue's location map 412 may be shown.Alternatively advertisements for similar event which may be of interestcould also be displayed.

As discussed hereinbefore, the dynamic entry code will comprise aninoperable state and a functional state. In FIG. 4a , the dynamic entrycode is in its inoperable state and an inoperable entry code 404 isdisplayed. In FIG. 4b , the dynamic entry code has been transitionedfrom its inoperable state to a functional state and the functional entrycode 408 is available on the mobile user device. In this example, thedynamic entry code is a Quick Response (QR) code. Therefore, theinoperable entry code 404 does not display any QR code or only displaysa portion of the QR code; and, the functional entry code 408 displaysthe QR code in a format which can be read by a scanner at an event. Itwill be appreciated that, when the dynamic entry code is a visual codesuch as a QR code or a barcode, the venue is not required to use theticketing system venue app and can simply use legacy scanners which mayalready be installed. In a preferred embodiment, the visual code may beanimated such that the QR code or barcode is animated to prevent screenshots being taken of the visual and being subsequently used in afraudulent manner. In this case, once the event staff have scanned thedynamic entry code successfully and the legacy scanner indicates thatentry to the event is permitted, the event staff may interact with theelectronic ticket 400 held on the user's mobile user device in order toconsume the electronic ticket 400. This may be done by swiping acrossthe functional entry code and entering a PIN or alphanumeric code knownonly to the event staff which can be changed on an event to event basis.It will be appreciated that in the embodiment where the event staff areused to transition the ticket 400 from the inoperable state to thefunctional state through entry of a PIN code which is only known toevent staff, the entry of this PIN code may also serve as a way ofconsuming the electronic ticket 400 at the same time. Alternatively, inorder to mark the ticket 400 as consumed, the event staff could scan avisual code which is only in their possession. Any of these actions bythe event staff would trigger the electronic ticket 400 to be nowdisplayed as being consumed, as is shown in FIG. 4c . If the user'smobile user device is in communication with the ticketing server, thenthe consumption of the ticket 400 can be communicated to the ticketingserver. In a preferred embodiment, the venue will use the ticketingsystem venue app and the manual consumption of the electronic ticket 400by event staff will not be necessary. In this preferred embodiment, theticketing system venue app will be automatically notified of thesuccessful scan of the electronic ticket 400 and will inform theticketing server accordingly.

In a further preferred embodiment, the dynamic entry code may not be avisual code which is non-readable by a human, such as a QR code or abarcode, but could be a hidden alphanumeric key which uses a challengeresponse protocol. In such a system, the electronic ticket 400 willsimply show an indication such as “Not Ready”/“Ready” or“Inactive”/“Active” or “Wait”/“Proceed to entry point” on the electronicticket 400. The sign will indicate whether the electronic ticket 400 isin its inoperable state or its functional state. Once the electronicticket 400 has indicated it is in its functional state, the user canapproach the entry point for the event and event staff will use theticketing system venue app to send a challenge and receive a responsefrom the end user app on the user's mobile user device. In this way, theentry code is never displayed to the user at all and therefore makes itvery difficult for any fraudulent forging of tickets to take place. Thevalidation of the ticket at the entry point would be completed using thechallenge-response protocol.

FIGS. 5a and 5b show the verification of the electronic ticket 400 at avenue. FIG. 5a shows the process followed where the venue has access tothe ticketing system venue app 106, and FIG. 5b shows the processfollowed where the venue only has legacy scanners available at thevenue.

With reference to FIG. 5a , the user 500 who is attempting to gainadmission to the event will present their ticket using the end user at104 to a member of the event staff 502, as shown in step 504. The eventstaff 502 will read the dynamic entry code, which forms part of theelectronic ticket, using the ticketing system venue app 106 in step 506.The ticketing system venue app 106 may preferably be connected to a QRscanner or barcode scanner or camera capable of operating as same. Instep 508, the ticketing system app 106 will contact the ticketing server102 to verify that the electronic ticket is legitimate. The ticketingserver 102 will, in step 510, confirm that the electronic ticket islegitimate and also check if the user account holding that electronicticket is in a need-to-check state and if so will require the eventstaff 502 to check the identification of the user 500 who is attemptingto gain admission to the event. If the user account is in a verifiedstate, then there is no requirement for the event staff 502 to check theidentification of the user 500. The validity of the ticket istransmitted to the ticketing system venue app 106 in step 512, alongwith a notification for the event staff 502 to check the user'sidentification, i.e. a ‘need-to-check’ instruction, if necessary. Theticketing system venue app 106 notifies the event staff 502, in step514, of the validity of the ticket. The ticketing server 102 will alsoconsume the ticket, in the sense of marking the ticket as being a validand used ticket, and will send this information from the ticketingserver 102 to the end user app 104, as shown in step 516. The user 500is notified that the ticket has been concerned in step 518, by the enduser at 104.

In FIG. 5b , the user 500 who is attempting to gain admission to theevent will present their ticket using their end user app at 104 to amember of the event staff 502, as shown in step 522. The event staff 502will read the dynamic entry code, which forms part of the electronicticket, using a legacy scanner 520 in step 524. The legacy scanner 520will verify that the electronic ticket is legitimate by scanning avisual functional entry code on the electronic ticket, as indicated instep 526. The validity of the ticket is indicated to the event staff 502in step 528. This may be by way of a green light on the scanner 520. Theevent staff member 502 will then manually consume the ticket, asindicated in step 530, by interacting with the end user app 104 on theuser's mobile user device. In a preferred embodiment, this interactionwill require the input of a PIN in order to change the ticket to beingconsumed/used. The end user app 104 may communicate this on to theticketing server (not shown) if a data link is possible and will notifythe user 500 that the ticket has been consumed in any event as isindicated in step 532.

It will be readily appreciated that the transition of the dynamic entrycode from being in its inoperable state to its functional state is avery important part of the invention. This may be carried out in anumber of different ways including, but not limited to, transitioningthe dynamic entry code from its inoperable state to its functional stateat a predetermined time. If for example, an event has a start time of8.00 pm, and the entry point at the venue is opened at 7.00 pm, then thedynamic entry code may be transitioned from its inoperable state to itsfunctional state at 7.00 pm. The time may be taken from the mobile userdevice, or more preferably from the ticketing server or from thewireless network which the mobile user device is connected to.Alternatively, geo-fencing may be used to transition the dynamic entrycode from its inoperable state to its functional state. For example, thedynamic entry code may be transitioned once the mobile user device comeswithin 100 m of the entry point of the venue. It'll be appreciated thatmany mobile user devices comprise GPS means and similar locationdetermination means which will be utilized in this embodiment.Preferably, the dynamic entry code will require the mobile user devicestoring the electronic ticket to be in a certain geographical locationat or after a certain time in order for the dynamic entry code to thetransitioned to its functional state. This will minimize the opportunityfor a ticket tout to re-sell the electronic ticket. A furtheralternative is to use a broadcast signal which will be transmitted froma position adjacent the venue and will cause, when received by themobile user device, the dynamic entry code to be transitioned to itsfunctional state. In this way, the event organizers can decide when theentry codes for the tickets for the event will be transitioned intotheir functional state. It is foreseen to transition a subset of thetickets so that the permitted entry to the venue can be staggered. Forexample, tickets which are for seats at upper levels of a venue may betransitioned to a functional state before tickets which are for seats atlower levels in the venue. This may facilitate the lessening of anycrowding issues as many users attempt to gain entry to a venue at thesame time. In yet another embodiment, it is envisaged to require oftheir use of an activator which is physically present close to a venue.For example, this could require the end user app to scan a visual code,such as a QR code, adjacent an entry point for a venue in order totransition the dynamic entry code stored on the mobile users device fromits inoperable state to its functional state. It is also envisaged thatWiFi networks and the like which are geographically located could beused for transitioning the dynamic entry code from its inoperable stateto its functional state.

As will be readily understood, many different techniques can be used totransition the dynamic entry code to its functional state.

In another embodiment of the present invention, a user credibilityrating will be established for each user of the ticketing system of thepresent invention. The user credibility rating will be an indication ofthe genuineness of the user as a fan. If a user purchases a number oftickets and uses those tickets themselves and passes any user accountverification checks, then that user should have a relatively high usercredibility rating. If a user is seen to re-sell a large number of thetickets which they have bought, then such a user may be a ticket toutand would receive a relatively low user credibility rating. In oneembodiment, an electronic ticket will only be issued to a user if theuser credibility rating associated with the mobile user device is abovea predefined threshold. In a further alternative embodiment it isforeseen that the dynamic entry code will only be transitioned from theinoperable state to the functional state if the user credibility ratingassociated with the mobile user device is above a predefined threshold.The threshold is adjustable and may be set by the third party or by theticketing server. The user credibility rating is calculated based on auser's historical ticketing transactions, and, the user's historicalticketing transactions comprise one of more of: number of ticketspurchased; aggregate value of tickets purchased; number of ticketsre-sold; aggregate value of tickets re-sold; number of tickets used;aggregate value of tickets used; number of tickets not used; aggregatevalue of tickets not used. Thus, the user credibility rating may becalculated based on a ratio of the number of tickets re-sold as comparedto the number of tickets used, or, based on a ratio of the aggregatevalue of tickets re-sold as compared to the aggregate value of ticketsused. Alternatively, the user credibility rating may be calculated basedon a ratio of the number of tickets purchased as compared to the numberof tickets re-sold. It will be appreciated that the threshold fordetermining whether a user is genuine or suspicious can be adjusted andset to a pre-determined value. In one embodiment, a user credibilityrating of less than 0.95 would be seen to be suspicious which wouldtherefore allow a user to sell up to 5% of the tickets bought, or, tosell tickets having a value of up to 5% of the total value of thetickets which they have bought. It will be understood that giftingtickets away for free may be viewed as a re-sale of the ticket and becounted towards the calculation of the user credibility rating.

It is also understood that, in a preferred embodiment, the restrictionson a re-sale of a ticket may only be applied where the sale is betweentwo parties known to one another as this will raise the possibility thatfinancial compensation could be organized between the parties, outsideof the ticketing system of the present invention. If the re-sale is madebetween two parties, whose identities are not made known to one anotherduring the process, then any restrictions on such a type of sale may belifted and not applied.

In a further embodiment, the user credibility rating may be calculatedin a number of ways, using different algorithms. Purely by way ofexample only, one such algorithm would be:

${{User}\mspace{14mu}{Credibility}\mspace{14mu}{Rating}} = {1 - \frac{\Sigma\mspace{14mu}{value}\mspace{14mu}{of}\mspace{14mu}{tickets}\mspace{14mu}{resold}\mspace{14mu}{by}\mspace{14mu}{user}\mspace{14mu}{to}\mspace{14mu}{known}\mspace{14mu}{purchasers}}{\Sigma\mspace{14mu}{value}\mspace{14mu}{of}\mspace{14mu}{tickets}\mspace{14mu}{used}\mspace{14mu}{for}\mspace{14mu}{entry}\mspace{14mu}{to}\mspace{14mu}{events}\mspace{14mu}{by}\mspace{14mu}{user}}}$

It will be readily understood that the electronic ticket suitable forproviding entry to an event may or may not be stored on the mobile userdevice. It must be capable of being stored on the mobile user device,but it is not necessary for the electronic ticket to be stored on themobile user device. In particular, the dynamic entry code which formspart of the electronic ticket does not need to be stored on the mobileuser device. Indeed, it may be advantageous to make the dynamic entrycode, when in its functional state to be unavailable to a user; and, bynot storing the dynamic entry code on the mobile user device, thisobjective could be achieved as the dynamic entry code would be notpresent. In such an embodiment, the inoperable state of the dynamicentry code would be stored on the mobile user device and when thedynamic entry code had to be transitioned from the inoperable state tothe functional state, the dynamic entry code in its functional statewould be received and stored onto the mobile user device. Of course, itis further envisaged that the dynamic entry code, even in both of itsversions: inoperable state and functional state, is stored on the mobileuser device but with the dynamic entry code in its functional statebeing unavailable to the user. This could be storing the dynamic entrycode in its functional state in a secured, potentially encrypted,partitioned section of memory on the mobile user device. In such amanner, the dynamic entry code, and in particular, in a preferredembodiment, the functional state of the dynamic entry code will be madeunavailable and/or inaccessible.

The terms “comprise” and “include”, and any variations thereof requiredfor grammatical reasons, are to be considered as interchangeable andaccorded the widest possible interpretation.

It will be understood that the components shown in any of the drawingsare not necessarily drawn to scale, and, like parts shown in severaldrawings are designated the same reference numerals.

It will be further understood that features from any of the embodimentsmay be combined with alternative described embodiments, even if such acombination is not explicitly recited hereinbefore but would beunderstood to be technically feasible by the person skilled in the art.

The invention is not limited to the embodiments hereinbefore describedwhich may be varied in both construction and detail.

What is claimed is:
 1. An electronic ticket suitable for providing entryto an event, the electronic ticket being stored on a mobile user device,wherein the electronic ticket comprises a dynamic entry code for theevent such that the dynamic entry code is transitionable from aninoperable state to a functional state, whereby entry to the event isonly possible when the dynamic entry code has been transitioned to thefunctional state; wherein, the dynamic entry code is a visual code whichis non-readable by humans, such that the inoperable state of the dynamicentry code prohibits the visual code from being displayed by the mobileuser device and the functional state of the dynamic entry code permitsthe visual code to be displayed by the mobile user; wherein, at the timeof purchase the electronic ticket is assigned to one or more of: aticket holder's name, a ticket holder's telephone number, and a ticketholder's device ID, such that, prior to allowing the dynamic entry codeto be transitioned from the inoperable state to the functional state,one or more of the ticket holder's name, the ticket holder's telephonenumber, and the ticket holder's device ID is checked to ensure a matchwith a name associated with the mobile user device, a telephone numberof the mobile user device, and a device ID of the mobile user device,respectively; and wherein at least a portion of the dynamic entry codein its functional state is unavailable to a user of the mobile device;and wherein at least a portion of the dynamic entry code is not storedon the mobile user device until a controlled trigger is activated, suchthat the controlled trigger, once activated, causes the remainingportion of the dynamic entry code to be received by the mobile userdevice, wherein receipt of the remaining portion of the dynamic entrycode at the mobile user device allows the dynamic entry code totransition from the inoperable state to the functional state.
 2. Anelectronic ticket as claimed in claim 1, wherein, the ticket holder'stelephone number assigned to the electronic ticket must match thetelephone number of the mobile user device in order to allow the dynamicentry code to transition from the inoperable state to the functionalstate.
 3. An electronic ticket as claimed in claim 1, wherein, theticket holder's telephone number assigned to the electronic ticket mustmatch the telephone number of the mobile user device in order to allowthe dynamic entry code to become stored on the mobile user device.
 4. Anelectronic ticket as claimed in claim 1, wherein, the dynamic entry codeis transitioned from the inoperable state to the functional state basedon an activator which is physically located adjacent an entry point ofthe event.
 5. An electronic ticket as claimed in claim 4, wherein, theactivator that causes the dynamic entry code to transition from theinoperable state to the functional state is under the control of theevent staff.
 6. An electronic ticket as claimed in claim 1, wherein, thedynamic entry code is transitioned from the inoperable state to thefunctional state if a user credibility rating associated with the mobileuser device is above a predefined threshold.
 7. An electronic ticket asclaimed in claim 1, wherein, the electronic ticket is marked as havingbeen used.
 8. An electronic ticket as claimed in claim 1, wherein, thevisual code is a Quick Response (QR) code which is only displayed on ascreen of the mobile user device when the QR code has been transitionedto the functional state.
 9. An electronic ticket as claimed in claim 1,wherein, the visual code is a barcode which is only displayed on ascreen of the mobile user device when the barcode has been transitionedto the functional state.
 10. An electronic ticket as claimed in claim 1,wherein, the dynamic entry code stored in the mobile user device may bealtered prior to the dynamic entry code being transitioned from theinoperable to the functional state.
 11. An electronic ticket as claimedin claim 1, wherein, the dynamic entry code is a hidden key which uses achallenge response protocol, such that in use it is indicated whetherthe electronic ticket is in its inoperable or functional state withoutthe dynamic entry code being displayed to the user.
 12. A method ofproviding an electronic ticket suitable for providing entry to an event,the electronic ticket being stored on a mobile user device, wherein themethod comprises: assigning, at the time of purchase, the electronicticket to one or more of: a ticket holder's name, a ticket holder'stelephone number, and a ticket holder's device ID; issuing theelectronic ticket, the electronic ticket comprising a dynamic entry codeto allow access to the event such that the dynamic entry code istransitionable from an inoperable state to a functional state; storingat least a portion of the dynamic entry code on the mobile user device,the dynamic entry code comprising a visual code which is non-readable byhumans; checking one or more of the ticket holder's name, the ticketholder's telephone number, and the ticket holder's device ID to ensure amatch with a name associated with the mobile user device, a telephonenumber of the mobile user device, and a device ID of the mobile userdevice, and only allowing the dynamic entry code to be transitioned fromthe inoperable state to the functional state where such a match exists;transitioning the dynamic entry code to the functional state to allowentry to the event; whereby, the inoperable state of the dynamic entrycode prohibits the visual code from being displayed by the mobile userdevice and the functional state of the dynamic entry code permits thevisual code to be displayed by the mobile user; and wherein at least aportion of the dynamic entry code in its functional state is unavailableto a user of the mobile device; and wherein at least a portion of thedynamic entry code is not stored on the mobile user device until acontrolled trigger is activated, such that the controlled trigger, onceactivated, causes the remaining portion of the dynamic entry code to bereceived by the mobile user device, wherein receipt of the remainingportion of the dynamic entry code at the mobile user device allows thedynamic entry code to transition from the inoperable state to thefunctional state.
 13. A method of providing an electronic ticket asclaimed in claim 12, wherein, the method further comprising the step ofchecking that the ticket holder's telephone number which has beenassigned to the electronic ticket matches the telephone number of themobile user device prior to allowing the dynamic entry code totransition from the inoperable state to the functional state.
 14. Amethod of providing an electronic ticket as claimed in claim 12,wherein, the method further comprising the step of checking that theticket holder's telephone number which has been assigned to theelectronic ticket matches the telephone number of the mobile user deviceprior to allowing the dynamic entry code to be stored on the mobile userdevice.
 15. A method of providing an electronic ticket as claimed inclaim 12, wherein, the method further comprises the step oftransitioning the dynamic entry code from the inoperable state to thefunctional state subsequent to an interaction with an activator which isphysically located adjacent an entry point of the event.
 16. A method ofproviding an electronic ticket as claimed claim 12, wherein, the step oftransitioning the dynamic entry code from the inoperable state to thefunctional state is carried out if a user credibility rating associatedwith the mobile user device is above a predefined threshold.
 17. Amethod of providing an electronic ticket as claimed in claim 12,wherein, the method further comprises a step marking the electronicticket as having been used, once the electronic ticket has been used toprovide entry to the event.